IMPORT <option> <interchange_file> <output>

 

converts an ARC/INFO export interchange file.

 

arguments

<option> - specifies the type of output to be created from the

interchange file.  The following options are available:

 

AUTO - automatically determines the correct import option from the

format of the export file.

 

COVER - a coverage, associated INFO data files and any index files.

 

FONT - an IGL font file.

 

GRID - an integer or floating-point grid.

 

INFO - an INFO data file.

 

LATTICE - a lattice file in the pre-6.0 lattice file format.

 

LINESET - a lineset file.

 

PLOT - a plotfile or graphics file.

 

MAP - a map composition created with the ARCPLOT map composer.

 

MARKERSET - a markerset file.

 

SHADESET - a shadeset file.

 

TEXT - an ASCII text file which becomes a system text file.

 

TEXTSET - a textset file.

 

TIN - creates a tin.

 

<interchange_file> - the prefix name of the ARC/INFO interchange file to

be converted.  A volume ID of .E00, .E01, and so on, will always be

appended to the given <interchange_file> to specify the file(s) to be

imported.  This will allow for importing coverages or files that are too

large to fit on one tape; for example,

 

RIVERS.E00, RIVERS.E01, and so on, up to RIVERS.E99.

<output> - the name of the output coverage, file or data set to be

created from the interchange file.  Pathnames can be used for all

options except FONT.

 

notes

IMPORT reads any export file which has been fully or partially

compressed as well as uncompressed.  IMPORT automatically recognizes

whether or not the export file is compressed.

 

For the COVER option, all INFO data files saved in the interchange file

whose names contain the coverage name prior to the last period in the

INFO data file name are written to the workspace INFO database for the

output coverage.

 

Any INFO pathname/user name can be specified as the output data file

when the INFO option is used.  However, the specified INFO directory

must exist prior to using IMPORT.

 

Use TAPEREAD and TAPEWRITE to create and read magnetic tapes containing

ARC/INFO interchange files to export data sets between different

computers.  Refer to the ARC/INFO System Dependencies Guide for your

computer for more details.

 

The AUTO option determines what is contained in an import file and then

imports it correctly; for example,

 

Arc: IMPORT

Usage: IMPORT <option> <interchange_file> <output>

Arc: IMPORT AUTO E4 XXXX

 Importing XXXX from interchange file E4.E00....

 Creating TIN XXXX

Arc:

 

 

different versions

As new data types are supported, new options are

added to the IMPORT and EXPORT commands to facilitate transfer to other

platforms running ARC/INFO.  Conflicts may arise when trying to import

data from one version of ARC/INFO onto a platform running an earlier

version of ARC/INFO.  There is no problem importing to a later version.

All export interchange files are upwardly compatible.

 

A problem may occur, however, going from a later to an earlier version.

The export file may contain a data set that is not available in earlier

versions, or the format of an existing data set may no longer be

compatible with earlier versions.  Also there are cases where the export

file will import correctly but the output cannot be used the same way.

 

Coverage index files and anything in double precision cannot be imported

to pre-5.0 versions of ARC/INFO.

 

Node attribute tables, routes, sections and annotation subclasses will

import into versions prior to Rev 6.0 as associated INFO data files for

the output coverage but will not function the same way they do at Rev

6.0.

 

Graphic files and map compositions generated in Rev 6.0 using the (1040)

format are not supported by earlier versions of ARC/INFO.

 

The LATTICE option converts a pre-Rev 6.0 lattice file.  Use the

LATTICE60 command to convert the imported pre-6.0 lattice file to a

lattice that can be used with the Rev 6.0 TIN software package.

 

At Rev 6.0, lattices are stored using the GRID data model.  The GRID

option is used to import an interchange file containing a surface grid

lattice.  A surface grid lattice cannot be imported onto platforms

running earlier versions of ARC/INFO.

 

You cannot import a 6.0 tin onto a platform running an earlier release.

Beginning with TIN 6.0, the x,y coordinates for the tin  nodes are

stored in double precision.  The Rev 6.0 tin data model supports break

lines and non-convex hulls.  These enhancements are not supported in

earlier releases.

 

The format of all symbol set files changed at Rev 6.0 and will not be

compatible with earlier versions of ARC/INFO.

 

ADD files can be imported but must be rebuilt using ADDRESSBUILD.

 

 

discussion

An ARC/INFO interchange file can be used to transport coverages, INFO

data files, text files such as AML macros, and other ARC/INFO files

between various machine types (e.g., from a Prime computer to a DEC VAX

computer).  An interchange file contains all coverage information and

appropriate INFO data file information in a fixed-length ASCII format.

 

There are many ways to use IMPORT.  One way is to transport a coverage

and its associated INFO data files.  Each coverage file and its INFO

data files are read from the interchange file into an output coverage.

This is done by using the keyword COVER for the first argument.  Another

way to use IMPORT is to transfer an INFO data file.  In this case, any

INFO pathname/user name can be used to specify the name of the output

INFO data file.  This option is invoked by using the keyword INFO for

the first argument.  A third way is to use IMPORT with the TEXT option

to transfer key files, AML macros and other text files.

 

The EXPORT command is used to create an interchange file.  The

interchange file can be transferred by tape to another machine where

IMPORT can be used to re-create the coverage, text, INFO file, or other

data type.

 

The IMPORT and EXPORT commands can also be used to back up individual

coverages to tape for archiving (as opposed to backing up entire user

workspaces).  For example, individual coverages corresponding to map

library layers within a single tile (i.e., map sections) can be archived

to tape and restored to disk only as they are needed.

 

If multiple volumes are provided by EXPORT, the ASCII interchange file

name for IMPORT must be in the format <interchange_file>.E00 through

<interchange_file>.Enn, where nn is the last volume ID.  Even if only

one volume is produced, this file name must have the .E00 extension.

 

Four additional ARC commands, CARTREAD, CARTWRITE, TAPEREAD and

TAPEWRITE, provide you with the necessary tools to create and read

cartridges and magnetic tapes for transferring export files between

different machine types.

 

 

examples

The following example IMPORTs an interchange file named TRACTS.E00 and

creates a coverage named TRACTS in the STDYAREA workspace.

 

Arc: IMPORT COVER TRACTS [.STDYAREA]TRACTS

 

This example IMPORTs an interchange file named EXCOVPAT.E00 and creates

an INFO data file named EXCOV.PAT in the COVERS workspace.

 

Arc: IMPORT INFO EXCOVPAT.E00 [.COVERS]INFO!ARC!EXCOV.PAT



